Visitor Management
Complete visitor management from Knight Watch. Works with your existing access control.
Invite, screen, badge — nothing to switch off after. A visitor's badge should stop working the moment the visit ends, without anyone having to remember. Knight Watch visitor management runs on BAR: the host sends one invitation, a kiosk checks the visitor in, runs the NDA, safety video and photo in their own hands, and tells the host, and the credential they carry — a pass on their phone or a card from the site's pool — switches itself off when the visit is over. The experience is the same whatever access control system you run.
Open the deck · Download the PDFOne visit, start to finish
1. The host invites. From BAR, signed in with Microsoft Entra ID, with the site's rules attached: who, when, and what has to happen before they arrive. The visitor gets an email with their confirmation code. Groups arrive as a visitor event — a list imported once, every guest invited at once, one code each.
2. Induction happens at the kiosk, in the visitor's own hands. Whatever the site requires for that kind of visitor: sign the NDA, watch the safety video, complete a declaration or a short quiz, take the photo for their badge, fill in a custom form — on the kiosk, before check-in completes. Signatures are captured where required, a completed step stays valid for a set number of days so a regular visitor is not asked again every week, and a named person can be allowed to bypass a step.
3. Screening happens on registration. Every visitor is checked against your own watchlist. An external screening provider can be connected where your policy requires one.
4. The kiosk checks them in. A code or a walk-in, a photo, and the guest Wi-Fi on the done screen. Walk-ins register at the kiosk and the host is asked to approve. The host's phone is told the moment their visitor arrives — and an hour before, when they are due.
5. On site, then switched off. The visitor carries a pass on their phone or a card from the site's pool. When the visit ends the pass stops working and the card goes back in the pool; a job every fifteen minutes expires anyone still on the books past their departure time and switches their badge off. Check-out releases the card and revokes the mobile credential.
Phone or card — either dies on time
| Route | What happens | Status |
|---|---|---|
| HID Mobile Access | At check-in BAR creates the HID Origo user and credential; the visitor receives their invitation code by text message. Revoked at check-out. | Built and wired into the visitor flow. Enabled per deployment once your own HID Origo tenant is configured. Not yet running in a production tenant. |
| KnightPass | A visitor pass with an active window, from five minutes to thirty days, provisioned into Apple Wallet or Google Wallet through the WaveLynx Wallet API by a link sent as a QR code, email or text. The wallet platform stops honouring it when the window closes. | Running in production today on Knight Watch's own AWS account. |
| The pool card | A real, pre-encoded card that belongs to the site. At check-in BAR takes one from the Schneider Electric EcoStruxure Security Expert visitor pool and assigns it; at check-out the card goes back. Usage counts sync from the platform every five minutes. | Built and demonstrated end to end against a live Security Expert system. |
Your access control
The experience is platform-agnostic. The last step is not. Invitation, pre-check-in, screening, the kiosk, host alerts and the pass itself do not depend on the access control platform. Writing a credential to a door does:
- BAR drives Schneider Electric EcoStruxure Security Expert today — the visitor user, the pool card, sign-in and sign-out.
- KnightPass pushes provision, suspend and delete to any platform through its webhook adapter, which is the integration path available today. Its Security Expert and Lenel OnGuard adapters are written and deployed but not yet validated against a live panel.
- Anything else is a scoped driver, not a setting.
The kiosk
Knight Watch supplies, installs and services the kiosk. The software:
- keeps working when the network does not — check-ins and sign-outs queue on the device and sync when the connection is back;
- is branded, worded and languaged per facility;
- is locked to its facility with a device token and an address allow-list, and locks itself after repeated failed authentication;
- returns to the welcome screen on its own when left idle.
Not in the box today: badge printing at the kiosk (the physical route is pre-encoded pool cards, the other route a pass on the phone), ID-document scanning, and a visitor app — the visitor uses the kiosk and, for a phone pass, their wallet.
Alerts
Hosts are told by email, text message or Microsoft Teams when a visitor registers, is an hour away, arrives, checks out, or expires — and when a walk-in is waiting for their approval. Everbridge can be connected to reach everyone on site in an emergency.
KnightPass runs in production today on Knight Watch's own AWS account.
The visitor flow and the kiosk are built, not deployed. The visitor path — invitation, approval, pool card, check-in and check-out — has been walked end to end against a live Schneider Electric EcoStruxure Security Expert system, and the kiosk application is built. No customer is running the visitor kiosk in production today, so there is no reference call to offer yet.
External screening and Everbridge are connected per deployment and are off until configured. Support terms are set by the agreement you sign; no uptime figure and no response-time promise appears anywhere in this material. Where a vendor product is named, it is named because we integrate with it — not to imply a partnership, certification or endorsement.
See it on your own lobby
Book a thirty-minute demo. We will walk one visitor from invitation to expired pass, and tell you plainly what would have to be built for your access control. knightwatch.net
Knight Watch installs and services access control systems as an integrator. The people who wrote the check-in know what a visitor card does at the panel — which is why the card comes from a pool the platform already trusts.